docs: codify the agent-ready issue standard#4536
Closed
Hmbown wants to merge 2 commits into
Closed
Conversation
Capture the deconstruction convention the tracker already trends toward (.github/ISSUE_TEMPLATE/agent-task.yml) as a triage standard for existing issues: required body structure, anchor discipline, epic phasing, the maintainer-vs-community rework boundary, and community thread etiquette. Link it from AGENTS.md stewardship guidance and docs/ISSUE_TRIAGE.md so future triage rounds apply one standard. Written during the 2026-07-18 v0.9.2 lane triage round with agent assistance.
The v0.8.29 audit note documents writing \x1b[>1u directly on Windows as current behavior, but push_keyboard_enhancement_flags now probes with \x1b[>0u and enables no flags, decoding newline chords per terminal instead. Found while triaging #1687, where the stale note pointed at the wrong mechanism. Noted during the 2026-07-18 triage round with agent assistance.
Owner
Author
|
Harvested the useful agent-ready issue standard onto current main as #4860, with canonical contributor provenance in commit This draft is now superseded by the focused harvest; closing it keeps one reviewable concern and preserves the original history here. |
pull Bot
pushed a commit
to dolfly/DeepSeek-TUI
that referenced
this pull request
Jul 26, 2026
Capture the executable issue-spec convention and community triage boundary from PR Hmbown#4536 on current main. Harvested from PR Hmbown#4536 by @Hmbown Co-authored-by: Hmbown <101357273+Hmbown@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/AGENT_READY_ISSUES.md: the triage standard for making tracker issues executable by a fresh agent with no extra context — required body structure (Problem / Current evidence / Scope / Key files / Acceptance criteria / Verification / Out of scope / Related, plus Phases for epics), anchor discipline (every path verified,(anchor not found — needs discovery)convention), the maintainer-vs-community rework boundary (restructure our own bodies in place; never rewrite a reporter's body — comment instead), and community thread etiquette (specific thanks, honest status, no invented claims, bilingual asks for non-English reporters).AGENTS.md(stewardship section) anddocs/ISSUE_TRIAGE.mdso triage rounds apply one convention..github/ISSUE_TEMPLATE/agent-task.ymlalready established at filing time to the rest of the tracker; written alongside the 2026-07-18 v0.9.2 lane triage round that applies it.Testing
cargo fmt --all -- --check— not applicable, docs-only change (no Rust files touched)cargo clippy --workspace --all-features— not applicable, docs-only changecargo test --workspace --all-features— not applicable, docs-only changeChecklist
🤖 Generated with Claude Code
https://claude.ai/code/session_01QqiqBtPEFYi2rzqFH9V2yR
Generated by Claude Code